Last updated: 3 October 2026
AppSurge commv is responsible for the personal information described here. Contact us at [info@appsurge.app](mailto:info@appsurge.app) or at Sergeant Debruynestraat 38, Antwerpen
This policy covers our App Store and Google Play apps that link to it. Collection depends on the app, platform, version and features you use; not every app handles every category below.
- Your content: selected photos, videos, recordings, instructions, documents, notes, messages and other information needed for a feature.
- Accounts and purchases: sign-in details where accounts are offered, customer or installation identifiers, receipts, subscription status and purchase history. Apple and Google process store payments; we do not receive your full card number or security code.
- Usage and diagnostics: IP address, approximate location, device/app information, feature and purchase interactions, performance, errors and service records. Some records are linked to a customer or installation identifier rather than being anonymous.
- Feature-specific information: location, health or dietary information, religious activity, child profiles, measurements, contacts and financial documents, as described in section 5.
Information comes from you, your use of the app, authorized device services, sign-in/payment providers and services that return requested results. Local content may also be included in your device backups or optional cloud sync.
We use information to deliver requested features, manage purchases, provide support, review reports, understand app use, prevent abuse, maintain reliability and meet legal obligations.
Where European law applies, service delivery relies on performance of our contract with you; necessary security, troubleshooting and ordinary support rely on legitimate interests, subject to your rights; legally required records rely on legal obligations. Consent applies to processing covered by a valid permission you give. Analytics requires consent where applicable; otherwise, any reliance on legitimate interests must respect your rights and applicable device-access rules. Protected health or religious information also requires an additional legal condition, such as explicit consent. This policy does not itself provide consent.
AppSurge does not use customer information for off-app advertising, email marketing or training AI models. This describes our use; third-party processing and retention depend on the applicable service arrangements.
We use providers for these specific purposes:
- AI processing: OpenAI for supported analysis, transcription and assistance; Replicate and fal.ai for supported media generation; Google Gemini in applicable legacy features. Section 5 identifies the relevant apps. Platform speech services may also process audio remotely.
- Cloud hosting and account storage: processing submitted content, storing accounts or cloud history, and maintaining service/security records. Apple or your device-backup provider handles enabled sync and backups.
- Purchases and analytics: app stores and subscription/paywall services receive purchase, identifier and interaction information; app-usage and diagnostic services receive the events described below.
- Support and moderation: email and third-party support-messaging services handle reports, attachments and relevant customer information. Operational alerts may contain request metadata or error details.
- Feature content: product databases, weather/maps, prayer resources and wildlife-information services receive relevant searches, downloads or location requests.
We may disclose necessary information to comply with binding legal requirements, protect rights and safety, or in a business transfer subject to applicable protections. Exports, external websites and recipients you choose have their own privacy practices.
Selected images and instructions are processed by Replicate or fal.ai; legacy processing may use Google Gemini. Saved results are local; customer-linked instructions, usage and diagnostic records can remain on our services. Android and some earlier iOS versions use additional usage analytics. Submitted safety reports include the generated image, instructions and your explanation, excluding original/reference photos.
Portraits, reference images and styling choices are processed by Replicate. Saved looks can include originals and results. Separately agreed support reports can include before/after photos and customer details sent through a support-messaging service. Private-session mode does not guarantee immediate provider-wide deletion.
Baby photos and selected milestone text are processed by Replicate. Profiles can include names, birth dates and milestones. Optional Apple cloud backup includes profiles and images. The app is intended for adults acting for a child.
Ordinary measurements stay local. Optional AI try-on sends hand and ring images to Replicate. Device verification, purchases and usage limits involve service records; optional analytics concerns app events.
Room/reference photos and design instructions are processed by fal.ai. Projects and results are also saved locally. Selected shopping links contact external retailers.
Account details, uploaded media and generation/purchase history are stored online. Images and instructions are processed by Replicate. Use the account-deletion control to request account and associated storage removal.
Recordings, documents, images, transcripts and chat context can be sent for OpenAI processing. Replicate supports certain generated audio/visual features. Live conversations send microphone audio for processing; recording may continue in the background when started. Notes are also local. iOS includes usage analytics; local deletion does not erase all remote records.
Product databases receive barcode/search requests. Optional OpenAI explanations include relevant product and selected allergen information. Product/usage analytics is collected. Where available, improvement submissions include product results and a customer identifier and are enabled unless switched off. Use **Help improve FoodCheckr** and **Delete submitted data** to control these submissions separately from local history.
Product databases receive barcode/search requests. Prayer services receive coordinates and calculation preferences. Preferences/history are local; Android explanations use on-device models. iOS includes usage analytics. Product reports are sent through a support-messaging service on iOS or an email you choose to send on Android.
Product databases receive barcode/search requests; saved preferences/history are local. iOS nearby-place features use location and map services. Product reports go to a support-messaging service and can include your explanation, product details and customer identifier.
Food, weight, hydration and activity records are local, with optional Apple Health integration. Photos and descriptions used for nutrition analysis are sent to OpenAI. Optional usage analytics and product-database lookups are separate.
Photos and analysis instructions are processed by OpenAI; supported edits use Replicate. AI coaching can include facial estimates, food, hydration and sleep context, including authorized Apple Health summaries. Local wellness history and usage analytics are separate from this processing.
Location supports weather/maps. Optional skin analysis sends a photo and skin-type context to OpenAI. Analytics can include skin type, undertone and tan-level attributes. Its analytics setting is enabled by default in versions using that setting; turning it off stops future collection through that control.
Migraine, symptom and medication records are local. Optional Apple Health access includes sleep, heart-rate, menstrual and wrist-temperature information. Opt-in analytics can include headache type, pain/duration ranges and symptom/medication counts. Weather features use location.
Facial geometry and prescription recognition are processed locally. Saved measurements may include photos and prescriptions. Optional Apple iCloud sync includes this saved history; disabling sync does not delete existing cloud copies.
Workout history is local. Optional Apple Health integration accesses workout, heart-rate and energy information and can save workouts. External providers supply exercise and voice resources.
Caregiver-entered names, birth dates, feeding, sleep, milestones and developmental records are local and may enter device backups. These records can include a child's health information.
iOS stores selected-app blocking settings and progress locally. Recitation audio is processed locally, but analytics receives verse references, sequences, timing and recognition statistics that can reveal religious activity. Android uses installed-app selection, Accessibility, Usage Access and overlay permissions for chosen app limits; its blocking records stay local. Content downloads contact religious-resource providers.
Lessons and progress are local. Pronunciation practice uses speech services that may process audio remotely. Optional analytics concerns usage and technical events rather than raw answers or transcripts.
Photos are processed by OpenAI. Bird Identifier can also send text descriptions and precise coordinates to OpenAI for identification or seasonal advice. Weather/species services receive relevant location queries. Saved observations and photos are local.
Documents and reading progress are stored locally on your device. When you request a translation, the text you choose to translate and your target language are sent over HTTPS through our Cloudflare-hosted service to OpenAI to generate the translation. Translation requires an internet connection. Premium cloud speech sends selected text and voice settings to our speech-processing service. Supported on-device voices and document recognition run locally. Importing a web page contacts that website. Content submitted for cloud processing is subject to the service-provider and retention provisions in this policy.
Documents and reading progress are local. Web-page imports contact the selected website; device backups and chosen file providers may hold separate copies.
Recordings and edits are local. Transcription uses on-device models where available; supported platform-speech fallbacks can process audio remotely. Sharing creates separate copies.
Client/contact details, invoices, tax information, signatures and receipts are local. Exports share selected documents with the destination you choose.
Selected contact details and reminders are local. Calling or messaging passes the selected number to your chosen phone or messaging service.
This section describes Tapper for iOS version 1.0.6 and later versions that provide these privacy controls. Earlier versions and other platforms may have different features and data practices.
Your browsing and automation content. Saved websites, routines, scripts, tap positions, entered text and screen recordings are handled on your device. Tapper's usage analytics do not upload website URLs, page content, typed text, tap coordinates, selectors, routine names or recordings. Websites you open still receive requests from your device and may use their own cookies and tracking technologies. Their privacy policies apply. Content you choose to export or share is sent to the destination you select.
Optional usage analytics. Usage sharing is on by default when no previous preference exists. You can switch it off during onboarding or in Settings → Privacy & usage → Share usage analytics. An existing choice to switch it off is preserved. Switching it off stops optional usage reporting and clears pending analytics on the device; it does not by itself erase previously received records.
When sharing is on, we receive a random installation identifier and usage information such as features and modes used, app and paywall interactions, action counts, run durations, completion or failure reasons, subscription access state, timestamps and configuration version. Records also contain app version and build, operating-system version, device family, language and the part of Tapper being used, such as the app or Safari extension. We use these records to understand adoption, find problems and improve Tapper. A random identifier is pseudonymous: it is not your name, but it allows records from the same installation to be connected.
Optional questions.You may select a broad reason for using Tapper, such as games, reading, updates, repetitive tasks, testing or exploring, and answer whether Tapper helped with a task. These answers help us improve the app. Your selected purpose is saved locally. It is shared when usage sharing is enabled; if sharing is off, it stays on your device and may be shared if you later enable sharing. You can change your choice in Privacy & usage.
Bug reports and feedback. Reports are sent when you choose to submit them, including when optional analytics is off. We receive your message, selected topic, report reference, optional reply email, installation identifier, app version/build, iOS version, device model and family, language, RevenueCat customer identifier, subscription status and app configuration version. Reports also identify test/simulator versus production environments. We use this information to understand the problem, investigate subscriptions and respond when you provide contact details. The form lets you view the included support details. Please do not include passwords, payment-card details or private website content in your message.
Purchases. Apple processes purchases. RevenueCat helps us validate purchases, restore access and manage subscriptions using customer identifiers, transaction and product information, and subscription status. We may also receive subscription events in our support and administration service. Tapper does not receive your full payment-card details. Purchase information has its own retention and account controls; deleting Tapper analytics does not cancel a subscription or delete Apple or RevenueCat purchase records.
Remote settings and service security. Tapper loads remote settings even when optional analytics is off so that feature availability, fixes and in-app configuration continue to work. These requests include an installation identifier, platform, app version, language and app surface. Our service providers process the connection information needed to deliver and protect these services. Our API uses a salted hash of an IP address for rate limiting instead of storing the raw IP address in that rate-limit database. Cloudflare hosts the administration API and its data storage. RevenueCat provides subscription infrastructure, and Apple provides purchase processing. Access to the administration dashboard is restricted to authorized administrators. We do not use these Tapper records for third-party advertising tracking or sell them to data brokers.
Retention and deletion. Our daily cleanup removes usage events older than 90 days and feedback reports older than 365 days. Installation records are removed after 180 days without recorded analytics activity, measured from the last activity or registration. Cleanup timing means records may remain until the next scheduled cleanup.
You can choose Delete my analytics data in Privacy & usage. A successful deletion turns off usage sharing, removes the installation's server-side analytics records, and removes its installation link, reply email and RevenueCat identifier from associated feedback reports. The feedback message and remaining diagnostic details are retained for support until their normal deletion date. Personal information you typed into the message is not automatically removed from that text. If deletion cannot reach the service, sharing is switched off and the app asks you to retry.
For a request to delete feedback text or other support information, contact info@appsurge.app, preferably with the report reference. Subscription and billing records are separate from analytics and are retained as needed to operate subscriptions, resolve disputes and meet applicable recordkeeping obligations. They are not covered by the analytics deletion button or the 90-day analytics cleanup. You may continue to use local routines after deleting analytics and may later choose to send a new support report or enable analytics again.
Photos, recordings, health estimates and religious activity can be sensitive even without an account name. Facial processing for measurement or image generation is different from identifying someone through biometric authentication. Submit others' information only with appropriate authority.
Our apps are not directed specifically to children under 13. Baby-related features are for parents or authorized caregivers and can process children's information. Contact us about information submitted without appropriate authority. Age and parental-consent requirements depend on applicable law.
- Saved content: local items remain until removed or cleared; cloud accounts/history remain for the service until removed through applicable controls or a valid deletion request, subject to lawful retention. Backups and exports are separate.
- AIPGEN safety reports: retained for 90 days.
- FoodCheckr improvement submissions: scans for 365 days; reports while open and for 365 days after closure. Linked evidence follows report retention; limited deletion markers prevent resubmission of removed records.
- Support, usage and security records: kept as needed for investigation, follow-up, reliability, abuse prevention and legal claims. They can outlast a generated result.
- Purchases: retained as necessary for subscriptions, restoration, refunds and legal recordkeeping.
- AI processing: providers can retain content or security records beyond completion. Retention depends on the service and applicable settings; immediate deletion is not guaranteed.
Deleting an image, uninstalling an app or disabling sync does not automatically erase provider records, submitted reports or backups. Use the relevant local/account/cloud controls or contact us for server-held data. Android system **Clear storage** removes local app data. Deletion does not cancel a subscription; manage subscriptions through the purchasing store.
You can manage device permissions and available analytics/sync settings. Permission withdrawal affects future access, not previously submitted information. Some permissions or content are necessary for the feature you request; declining them can prevent that feature from working. Android recognition libraries can send technical diagnostics even when image recognition runs locally. Declining optional analytics does not stop necessary purchase/security processing.
Depending on applicable law, you may request access, correction, deletion, restriction or portability; object to processing; withdraw consent; use an authorized representative; or appeal a refusal. Withdrawal does not invalidate earlier lawful processing. We may verify your identity proportionately and will not unlawfully discriminate for exercising rights.
Email [info@appsurge.app](mailto:info@appsurge.app), identifying the app and relevant account/report reference. GDPR requests normally receive a response within one month; permitted extensions will be explained within that month. You may complain to your local authority or Belgium's [Data Protection Authority](https://www.dataprotectionauthority.be/citizen/actions/lodge-a-complaint).
Providers may process information outside Belgium and the European Economic Area, including in the United States. Transfers restricted by European law require an applicable legal mechanism, such as an adequacy decision or approved safeguards. Contact us for details relevant to your app.
We use appropriate security measures, but no system is completely secure. Information you export or share is also subject to the destination's protections.
We update this policy and its date when practices change, providing additional notice or seeking consent where required. A policy update does not itself authorize a new use of your information.